-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename split_line -> splitLine in InstrumentTXTResultsFileParser for consistency #2445
Conversation
keep the same class-method name in "class InstrumentTXTResultsFileParser(InstrumentResultsFileParser)", as in "class InstrumentCSVResultsFileParser(InstrumentResultsFileParser)"
Update resultsimport.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the consistency change @fengyundeng!
Would you mind to add a changelog entry on top of the file https://github.com/senaite/senaite.core/blob/2.x/CHANGES.rst with the updated title?
Hi @ramonski , the CHANGES.rst is updated. |
Hi @fengyundeng, The update to the changelog are not yet pushed to this PR, see Regarding your question:
Please always put your changelog above the others, so that we have a proper order. Thanks! |
Hi @fengyundeng, |
Hi @ramonski , i tried to, but i didn't find where to add CHANGES.rst to "Files changed" in this PR. |
Hi @fengyundeng, |
Description of the issue/feature this PR addresses
Linked issue: https://github.com/senaite/senaite.core/issues/
Current behavior before PR
class InstrumentCSVResultsFileParser(InstrumentResultsFileParser)
def splitLine(self, line)
class InstrumentTXTResultsFileParser(InstrumentResultsFileParser)
def split_line(self, line)
Desired behavior after PR is merged
keep the same class-method name in "class InstrumentTXTResultsFileParser(InstrumentResultsFileParser)", as in "class InstrumentCSVResultsFileParser(InstrumentResultsFileParser)"
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.